Part:BBa_K608406

Precipitator

Protein domain of Precipitator. Artificial Leucine Rich Repeat(LRR) with C and N-terminal hagfish domain fragments capping the artifical middle part. This part is one version of three different designed to bind nickel by histidines, grouped together pointing away from the horseshoe shaped protein.

Protein sequence CPSRCSCSGTEIRCNSKGLTSVPTGIPSS ATRLELESNKLQSLPHGVFDK LTQLTKSNNHLHSLPDNLPAS LEVLDVSNNHLHSLPDNLPAS LEVLDVSNNHLHSLPDNLPAS LEVLDVSNNHLHSLPDNLPAS LEVLDVSNNHLHSLPDNLPAS LEVLDVSNNHLHSLPDNLPAS LKELALDTNQLKSVPDGIFDR LTSLQKIWLHTNPWDCSCPRIDY LSRWLNKNSQKEQGSAKCSGSGKPVRSIICP
Colorcode (same in the sequence and video) green spheres: conserved Aminoacids Leu, Pro, Asn Histidin N-terminal Hagfish capcap C-terminal Hagfish cap artifical LRR domain fragment

Bacterial LRR Consensus of the central LRR fragment:

LxxLxLxxNxLxxLPxxLPxx

This protein can be used to complex Nickel or Cobalt. The principal mechanism is comparable to Ni-NTA columns, as chelates the ions. Free binding sites of the ions are then exposed, so that a His-tagged protein can attach to them. The design of the protein is of a particular interest, too. LRR are highly conserved motifs throughout evolution. They appear in all kingdoms of life in almost every thinkable role (Ligases, Receptors, Toxins etc.). Their core is highly conserved and provides a very stable backbone, while the intermediate, non-conserved aminoacids are almost freely interchangeable.

This protein can be used to complex up to 4 Nickel or Cobalt. However the principal design oft he protein is of a particular interest, too. LRR are highly conserved motifs throughout evolution. They appear in all kingdoms of life in almost every thinkable role (Ligases, Receptors, Toxins etc.). Their core is highly conserved and provides a very stable backbone, while the intermediate, non-conserved aminoacids are almost freely interchangeable.

We only submitted one of the three versions, to reduce redundancy in the registry. Please contact us for any questions.

Mathematical modeling[http://2011.igem.org/Team:Freiburg/Modelling]

To determine the Affinity k_D, experiments to find out the binding affinity of the [http://2011.igem.org/Team:Freiburg/Description#Plastic_binding_domain plastic binding domain] are necessary. To get a direct access to these values, we cloned the plastic binding domain in front of a GFP. Then, dilution and washing assays could be performed on polystyrene microtiter plates, red out by a fluorescence plate reader. The desired parameters could be calculated by measuring dilution rows of GFP proteins and measuring the fluorescence signals at the different concentrations. C_total could be determined by a dilution row with subsequent washing steps, to find out at what [P] concentration there is a saturation. See description of the plastic binding subproject for more detailed explanation on the experimental setup.

A qualitative experiment to prove that Nickel is binding the Precipitator is sufficient, since k_2 >> 1 and does not play a significant role in our setup. This experiment could have been done using a nanofilter that blocks protein but let through ions. The Nickel concentration of the flow through can then be measured.

Alternatively purification of the Precipitator by fusing it with a [http://2011.igem.org/Team:Freiburg/Results#Precipitator_fused_with_GST_tag GST-tag] could be done, to subsequently measure the absorbance of the protein, before and after adding Nickel to the solution. After Jordan 1974 a detectable change in the absorbance should be detectable after the complex is formed. A similar effect – a colorshift from white to blue - is visible when one prepares a Ni-NTA column. For this purpose we cloned the GST domain in front of the Precipitator. However towards the end of the project there was no more time to perfom these experiments.

Results[http://2011.igem.org/Team:Freiburg/Results#Plastic_binding_domain]

Sequence and Features

Assembly Compatibility:

• 10
  COMPATIBLE WITH RFC[10]
• 12
  INCOMPATIBLE WITH RFC[12]

  Illegal NheI site found at 274
  
• 21
  INCOMPATIBLE WITH RFC[21]

  Illegal XhoI site found at 100
  
• 23
  COMPATIBLE WITH RFC[23]
• 25
  INCOMPATIBLE WITH RFC[25]

  Illegal AgeI site found at 732
  
• 1000
  COMPATIBLE WITH RFC[1000]